More Pages: Daniels Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100


The best intermediate level Mechanical Desktop Book
Mechanical Desktop 6.0Mechanical Desktop 5.0


Excellent descriptions of the command options.
A must for beginners needing more than the Desktop Tutorial

extraordinary insight into 20th century america
A Champion of America

Stories that ring true
Gorgeous short stories!

Required for Owners
Excellent Original Literature

It was great!
AWESOME!

A Legacy Migration ClassicA well-defined plan of migration is presented early on for a complex retail supply system migration. Each phase of the plan is presented and explained in detail - covering both management and development perspectives equally well. For those of us who spend our days in a developer's world, the additional information on managing the migration effort contributes the right mix of information for what we are tasked to accomplish. I appreciated the technical specifics that were included throughout (i.e., utilizing Enterprise Java Beans) so that I didn't need to use my imagination as to how this plan would fit into my current project. Everything you need to know about legacy migration and then some is covered in this book. I knew that when I started to agree with what I was reading (aka Been There Done That) and could relate what was in the book to my own experience that I had found a winner.
This book is a good read and a great reference guide to help you get through a large, complex legacy migration. When you finally finish the book, take another look to capture all the detail you missed on your first read-through.
Methodical Resolution of Pivotal IssuesThe book describes, rationalizes, and selectively illustrates the RMM Approach, where the continued availability of the legacy system capabilities is necessary over the sequence of modernization increments. While the approach is illustrated through an incremental transformation of a legacy COBOL-based system to a Java-based derivative, the RMM Approach is nevertheless applicable to other modernization problems or technologies. Moreover, the book does an exceptionally good job of interweaving explanations with examples. These examples are modest but salient and revealing, thereby avoiding unwarranted detail or distractions.
The advocated approach is at once both architecture-centric and component-centric. Architecture centricity captures and sustains a rather specific vision of the as-desired system, and the associated target architecture provides a stable reference over the various modernization activities. Component centricity enables the identification, analysis, grouping, and ultimate realization of system elements that are allocated to the respective modernization increments. Overall then, the target architecture establishes the initial and termination points of a modernization project, and the componentization installments determine the actual redevelopment trajectory connecting the project end points.
For me, the most intriguing, innovative, and vital parts of the approach appear under the RMM activities labeled Define Modernization Strategy and Reconcile Strategy with Stakeholder Needs (Chapters 13-15 and Chapter 16, respectively). Basically, the modernization strategy provides a systematic approach to delineating, analyzing, and grouping modernization elements through an examination of the legacy system implementation, subject to project constraints and certain prior higher-level technical decisions. Then, the finalization of element groupings into sequential increments is determined using programmatic preferences of the various stakeholders. This two-stage definition of modernization increments is driven prominently by cost and risk considerations, as well as by programmatic and technical factors. Ultimately, the designated increments establish waypoints on the aforementioned redevelopment trajectory, thereby identifying interim architectural configurations that facilitate closure on the target architecture, while simultaneously maintaining user capabilities during the modernization effort.
In all, 'Modernizing Legacy Systems' is a readable, coherent, illuminating, and surprisingly broad treatment of a vital topic. Hopefully, the RMM Approach or variants thereof will see widespread use in industry, thereby exploiting "a systematic and fact-based method that avoids arbitrary, intuitive decision making..."


Great vocabulary and rhyming
Willy Joe Jehosephat's excellent adventure

Moonwatcher talks!"Moonwatcher's Memoir" rectifies this oversight, and then some. Richter had a great, exhausting time during his year (!) working on apes with Kubrick, and tells all. In doing so, he throws new light on the movie's timeline; it started shooting in Dec. 65, yet the long-planned ape scenes weren't shot until very late in the game: fall of 67 (the movie came out in April 68). How Kubrick kept his poise during such a long project remains, as the film might say, "a total mystery."
To use book review jargon, this book is a must for all Kubrick completists. You know who you are.
Moonwatcher's Memoir: A Diary of 2001, a Space Odyssey

Mosby's 1999-2000 IS THE BEST
A Must Have!
Im an Industrial Designer and I recomend this book and this software for all people envolved in product design.